Add consistent pagination support with limit/offset parameters #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
List endpoints lacked consistent pagination support. Several queries had no pagination parameters, and handlers used hardcoded limits.
Changes
SQL Queries
LIMIT/OFFSETtoGetAllProjects,GetSharedUsersForDefinition,GetSharedUsersForInstancesqlc generateRequest Models
limit(default: 100, max: 200) andoffset(default: 0) to:GetDefinitionSharedUsersRequestGetInstanceSharedUsersRequestHandler Functions
Limit: 999with appropriate pagination:input.Limit/input.Offsetfrom requestmaxSharedUsersPerQueryconstant (1000)maxAdminQueryLimitconstant (999999)Example
Pattern
User-facing list endpoints now accept query parameters. Internal operations use named constants to maintain correct authorization semantics.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.